home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d20
/
trksds42.arc
/
TRACKM.DOC
< prev
next >
Wrap
Text File
|
1991-06-30
|
87KB
|
2,331 lines
▒▒▒▒▒▒▒▒▒▒▒█ ▒▒▒▒▒▒▒▒▒█ ▒▒▒▒▒▒▒▒▒▒█ ▒▒▒▒▒▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█
▀▀▀▀▒▒▒█▀▀▀▀ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█▀▀▀▀▀ ▒▒▒█ ▒▒▒█ ▒▒▒▒ ▒▒▒▒█
▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒▒▒▒▒▒▒▒█
▒▒▒█ ▒▒▒▒▒▒▒▒▒█ ▒▒▒▒▒▒▒▒▒▒█ ▒▒▒█ ▒▒▒▒▒▒▒█ ▒▒▒█▒▒█▒▒▒█
▒▒▒█ ▒▒▒█▀▀▀▒▒▒█ ▒▒▒█▀▀▀▒▒▒█ ▒▒▒█ ▒▒▒█▀▒▒▒█ ▒▒▒█▀▀▀▒▒▒█
▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█
▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█
▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒▒▒▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█
▀▀▀▀ ▀▀▀▀ ▀▀▀▀ ▀▀▀▀ ▀▀▀▀ ▀▀▀▀▀▀▀▀▀ ▀▀▀▀ ▀▀▀▀ ▀▀▀▀ ▀▀▀▀
Version 4.20
Copyright (c) 1990/91 by Ulrich Bartelt
ALL RIGHTS RESERVED
FidoNetnode 2:241/5801
FroDo-Help 2:24/4
TrackM Usermanual Version 4.20 page - 2 -
Table of contents:
Introducing TrackM 3
Features of TrackM 4
Licensing Information 6
After registering 7
Trademarks 7
Hardware 8
TMSETUP 8
Running TrackM 9
Multiple language support 11
PointNet Remapping 11
Logging 12
Environment 12
EXPLANATION OF TMSETUP'S VERBS 13
Nodelist 15
Private-Node Manager 15
Languages 18
Timezones 18
AreaFix / AreaMgr / Raid 19
Names and Errorlevels 20
Messagebits 21
Message clean-up 23
The Pointnet 25
Interzonehandling 26
User definable Text 27
Templates 28
THE MANAGER-SECTION
The Point Manager 29
The ReAddress-Manager 30
The User-Manager 31
The Disturb-Manager 32
The Asshole-Manager 33
The Exclude-Manager 34
The Request Manager 35
The Route-To Manager 37
The Route-From Manager 37
TrackM Reminder 38
Errorhandling 39
REGARDS 40
Distribution Systems 41
INDEX 42
TrackM Usermanual Version 4.20 page - 3 -
┌───────────────────┐
│Introducing TrackM │
└───────────────────┘
TrackM is a three-in-one program:
I. A powerful message-tracker and point-manager!
TrackM was originally made to check your NetMail for messages
with unknown origin or destination addresses.
TrackM considers all addresses of messages in your NetMail-
directory with an internal index, build from your nodelist
file(s). If someone wants to send a message through your
system to a unlisted node TrackM will return it to the sender
with a comment. On the other hand if a message reaches your
system with an unknown origin address, a comment is added
that the receiver should not answer to this message via your
system. TrackM will keep your netmail directory clean.
Your uplink - normally your host - will like TrackM because
he don't get any message from you for people, not listed in
the nodelist.
If you are running a point, your boss will be glad, because
no wrong messages will reach him.
While TrackM is writing all information into a logfile, you
have an overview of messages that are going 'through' your
system. The receiving system can see when a message passed
your system, because TrackM adds a ^AVIA-line with a time-
stamp to the message. This is something like a path-line
known from EchoMail for NetMail.
II. A Remind-database manager!
Do you like to send messages to your friends when they have
birthday? Or do you like to have a program that reminds you
on your wedding day? You're just reading the introducion of
such a program!
TrackM can handle a database with an unlimited size of
records. Each record caused TrackM to generate a message if a
date in the record is matching the actual system date. You
can also generate file requests with the 'Remind-Manager'.
As a bonus for people using the Remote-Accsess BBS, I have
included a program in this packet, that automatically
generater and/or updates the remind-database from your
USERS.BBS file.
TrackM Usermanual Version 4.20 page - 4 -
III. A File-Request manager.
Do you have a high-speed modem like HST or PEP? And do you
have points without such a modem who bother you to request
files for them?
The 'Request-Manager' in TrackM allows your points (or to be
more general your slower downlinks), to request files via
your system. After your system has made the request
successfully the file will be forwarded to the requester. To
manage this, your downlinks must follow some rules which look
very similar to the rules handling with AreaFix/AreaMgr.
This manager is a bonus for people, taking the time to
register TrackM.
┌───────────────────┐
│Features of TrackM │
└───────────────────┘
o full-screen setup
o powerful remind database
o two different integrated languages
o multiple language support
o integrated point remapper !!!!
o multiple pointnet aware
o integrated messages renumbering !!!
o automatically networkmatching
o AreaFix / AreaMgr support
o RAX Point support
o can handle up to 10 different nodelists with automatic detec-
tion and recompilation if there are a changes in one of them.
The order of compiling the nodelist is up to you, so you can
have the most recent file up for scanning (normally your
pointnetlist)
o Private-Node Manager for addresses not in the nodelist.
o creates it's own IDX file that takes only about 2 bytes per
node so 25.000 nodelist-entries only take 50 KB of diskspace
TrackM Usermanual Version 4.20 page - 5 -
o If there is no need to change any message TrackM is able to
check 100 Megs in less than a second.
o can strip messagebits and/or messageflags
o can return missrouted echomail
o return mail marked as ORPHAN by external utilities like UUCP
gating software.
o short ! only takes 90 kilobytes of diskspace and runs with
less then 200 KB of system memory.
o exclude nodes from processing
o delete received filerequests
o delete sent messages
o move sent messages from the sysop
o delete received messages
o routing of files on a three-level inbound
o can add missing INTL-lines
o name remapping to points
o remap messages to YOU to a pointnode
o send a message to a given name anywhere
o copy a message to up to 5 cosysops
o readdressing of messages
o do not disturb function for exquisite nodes
o return of messages by from-name
o return of routed messages you have no uplink to
o no routing for systems you do not want to route messages for.
o user definable text of return messages
o easy way to change your pointnet without troubles
TrackM Usermanual Version 4.20 page - 6 -
┌───────────────────────┐
│ Licensing Information │
└───────────────────────┘
TrackM is the copright material of Ulrich Bartelt. It may only be
used in accordance with the conditions set in the following
license agreement:
- You may use TrackM for a period of four weeks on a trial
basis in order to determinate it's suitability for your
particular application. After this period you MUST register
TrackM.
- Group registrations are available, and are dealt with on a
case by case basis.
- Registration entitles you to use TrackM and any future
versions of TrackM for as long as you wish, subject to any
special licensing conditions attaches to future versions. For
details on the registering procedure, refer to the contens of
the special file REGISTER.DOC included in this packet.
- Ulrich Bartelt is in no way obligated to provide future
versions of, or support for, TrackM.
- You may not modify or otherwise reverse-engineer TrackM.
- You are encouraged to distribute TrackM provided that no fee
is charged for its distribution, and that the distribution
archive is not modified in any way. Pay-Bulletin-Board-
Systems may however charge their normal fee, provided that no
additional charge is levied for TrackM.
- TrackM may not be included as part of any software library
which is distributed on a registered basis without prior
written permission of Ulrich Bartelt. This expecially
includes all kinds of shareware distribution libraries.
TrackM Usermanual Version 4.20 page - 7 -
┌───────────────────┐
│ After registering │
└───────────────────┘
Upon registering you will receive your uniquely generated key.
Each key is a small file with exactly 200 bytes in size which
contains information about your registration. The name will be
something like 00FFEE00.KEY which represents your net/node number
written in hexadecimal code. To install the key, simply rename it
to TRACKM.KEY and copy it to the directory TRACKM.EXE resists.
NOTE: Your key contains binary information, so you have to
copy it in the binary form. If you notice any problems
please look at the copied TRACKM.KEY if the size is
still 200 bytes. If not, add /B to the copy command and
copy it ones again.
When TrackM detects a valid key it switches into registered mode,
identifying itself by placing a '+' after the version number. In
addition the full-screen set-up program TMSETUP.EXE will write out
a comment to whom it was registered.
Features marked in this manual with a '*' are only available when
TrackM is running in registered mode. These bonus features show my
appreciation of your taken the time to register it.
I would like to make it absolutely clear that TrackM is fully
functionable before it is registered; the bonus features only
provide you from using a bunch of other programs that can do the
job. The absence of this features makes TrackM no less usable.
TrackM is not and will never be "ExpireWare".
ATTENTION: Your key is unique, and under NO circumstances
should be made available to anyone else. Doing so,
is a direct violation of the agreement you entered
with me by registration.
┌────────────┐
│ Trademarks │
└────────────┘
The following products are copyrighted material and/or trademarks:
DESQview Quarterdeck Systems
Opus Wynn Wagner III
TosScan & FrontDoor Joaquim H. Homrighausen
BinkleyTerm Bit Bucket Software
FidoNet Tom Jennings
IBM International Business Machines
MS-DOS Microsoft Corporation
Remote Access Continental Software & Andrew Milner
TrackM Usermanual Version 4.20 page - 8 -
┌──────────┐
│ Hardware │
└──────────┘
TrackM and TMSETUP should run on any XT/AT/386 with DOS 3.2 or
higher. Both supports any videomodes up to a 132x60 display mode
with the exception of the internal TMSETUP-editor, which needs
80x25 mode.
TrackM needs as least 230 KB of free RAM. TrackM now only comes in
the overlay version. You will not see a OVR-file on your disk. The
OVR is build-in TrackM.EXE. Never try to run a program like PKLITE
on TrackM. It will destroy the OVR and I do not know what happens
if you invoke TrackM.EXE.
NOTE: This version of TrackM supports up to 28000
nodelistentrys. If you have run TrackM before, you will
notice that the IDX-file TrackM produces is about 2 1/2
times smaller than before up from version 4.20. AND
searching for a node in the IDX-file is up to 100 times
faster. If you previously had more than 13000 nodelist-
entries you will also save about 80 kB of RAM.
┌───────────────────────────────┐
│ The full-screen setup TMSETUP │
└───────────────────────────────┘
The heart of TrackM is the fullscreen-setup-program TMSETUP.
Everything you want TrackM to do you must tell TMSETUP. You may
find TMSETUP looking a 'little' like the setup of FrontDoor. The
reason is, I like the FrontDoor setup, it's easy to use and I
don't need to tell you how to manage the setup.
When you invoke TMSETUP you will find a lot of features you don't
have access to. This features are only valid in the registered
version of TrackM. But the remaining features will fit everything
you need to run a normal mailbox system with points. More about
the key at the end of this document.
Unlike previous version of this doc, I have put all features toge-
ther in the order they appear in the TMSETUP program regardless if
you need a key to run a feature. Functions that are only available
in the registered version are marked with a '*'.
TrackM Usermanual Version 4.20 page - 9 -
┌─────────────────┐
│ Running TrackM │
└─────────────────┘
TrackM commandline switches:
CHKIDX
There is a integrated nodelist checker in TrackM!
When giving CHKIDX on the commandline, TrackM will scan your
configuration file and if necessary compiles the IDX file.
Now you are prompted for nodelist addresses.
The nodelistchecker was built-in, because most of the
problems people had with TrackM, due to errors in the
nodelist files. TrackM requires nodelistfiles that match the
IFNA-Standard.
LOOKREQ
Look in the TRACKMRQ.BBS file to see outstanding filerequest
( see 'Request Manager').
RENUM
TrackM has an integrated renumber option. After doing every-
thing with your messages, you can tell TrackM to rebuild the
NetMail in ascending order. After renumbering, TrackM looks
for the environment string FD to see, if you run FrontDoor.
If found, TrackM will initiate a rescan of your NetMail.
Together with 'KillRec', 'KillSent' and 'CleanFReq' (sorry
only in the registered version), TrackM can do everything you
need for a NetMail clean-up.
REMIND
Invoke the reminder database. Only run TrackM once a day with
this option.
SET <msg#>
A single message already processed by TrackM is marked, so
that the message will be seen by TrackM in the next run.
UNSET <msg#>
A single message that would normally be processed by TrackM
in the next run will be protected from processing.
TrackM Usermanual Version 4.20 page - 10 -
PROTECT
All messages already in your netmail directory are protected.
It's a good idea if you install TrackM AT THE FIRST TIME and
your netmail is already in order to run TrackM PROTECT.
UNPROT
Simply deletes TRACKM.TIM in the message directory. That will
cause TrackM to scan ALL messages int the next run. But
TrackM does *NOT* touch a message it already has seen. To
totally recheck a message you must give SET #.
COMPILE
will force TrackM to compile the nodelist.
-g
TrackM will use GERMAN messages for netmail bouncing (see
also configverb 'Language').
-r
toggles the configverb DoRemapp
-l
also handles local entered messages
NOTE: TrackM will only check for a wrong destination address
and will not write a trackline to local messages.
-q
TrackM will run in quiet mode
-a<zone:net/node[.point]>
You can define the address TrackM should use on the
commandline with -A<zone:net/node> So if your network address
changes you don't need a new key at once. The point is
optional if you are not running a pointsystem.
TrackM Usermanual Version 4.20 page - 11 -
┌───────────────────────────┐
│ Multiple language support │
└───────────────────────────┘
TrackM can support any language. There are two built-in languages
in TrackM that can be chosen from TMSETUP: English and German.
(The Italian language was deleted because there were too many
files missing). If you choose one of the built-in languages and
you like the texts TrackM writes as default, you have nothing to
do.
How to install a different language:
On start-up, TrackM looks for a file named TRACKM.LNG. This must
be a plain ASCII-file and holds the strings TrackM uses when
creating messages. TRACKM.LNG must have *EXACTLY* five lines:
1. line : to-string
2. line : from-string
3. line : subject-string
4. line : start-string
5. line : end-string
Please see the examples for TRACKM.LNG which are in the
distribution packet.
If you are using the public version of TrackM you have to live
with the English or German defaults for the other texts.
TRACKM.LNG works in *ANY* version.
┌────────────────────┐
│ PointNet Remapping │
└────────────────────┘
TrackM will automatically remap mail from and to YOUR points.
TrackM will look for the environment string POINTNET. If you are
running FrontDoor you should already have set this string. On
other systems include your pointnet in TMSETUP
When finding a message to one of your points TrackM will remap it
to PointNet/Point. For example, if you are running PointNet 1000
and a message is addressed to Net/Node.2 it will be remapped to
1000/2
On the other hand, if a message comes from 1000/2 it will be re-
mapped to Net/Node.2
This behaviour is the normal pointremapping you expected if you
running a normal system with one pointnet. TrackM is able to
handle multiple pointnets in the registered version. For example
you can run a 'normal' pointnet in fidonet and, if you are running
also a registered environment, a different pointnet for your
registered points. For more about this set-up look for 'AKA' and
'Point-Manager' in this document.
TrackM Usermanual Version 4.20 page - 12 -
┌──────────┐
│ Logging: │
└──────────┘
TrackM will log it's activities in a LOG-file named TRACKM.LOG.
The format looks something like FrontDoor's format. You can tell
TrackM to use a different LOG-file in TMSETUP. So its possible to
merge your mailer's logfile and the TrackM-logfile.
┌─────────────┐
│ Environment │
└─────────────┘
On start-up TrackM looks for the string TRKMOPT in your environ-
ment. Here you can tell TrackM what kind of system you are run-
ning. Until now, TrackM knows the following options:
DBRIDGE - you are running D'Bridge
FRODO - you are running FrontDoor
BINKLEY - you are running BinkleyTerm
GOLDED - you are using the GoldEd message editor
Depending what system you are running, TrackM does a few things
different for every system. There are some special things for
FrontDoor or D'Bridge to do (f.e. checking Flags) that are not
necessary on a Binkley-System. So don't waste the time of a
Binkley-User with this things.
If you already have a string SET FD=<dir> (or SET DBRIDGE=..) in
your AUTOEXEC.BAT, you don't need to set-up TRKMOPT to tell TrackM
what system you are running. If not, put the following line in
your AUTOEXEC.BAT file:
SET TRKMOPT=FRODO (for the FrontDoor example)
If you set GOLDED, TrackM will check all messages at every run,
not only thouse, that are younger than the timestamp TRACKM.TIM.
This was nesessary because GoldED does not give a new timestamp to
a message when you first read it. TrackM gets a little slower when
you have set GOLDED, but the most recent speed-factor is your
harddisk, not TrackM.
To set more than one option to TRKMOPT you have to say f.e.:
SET TRKMOPT=DBRIDGE,GOLDED
TrackM Usermanual Version 4.20 page - 13 -
┌───────────────────────────────────┐
│ Explanation of TMSETUP's verbs │
└───────────────────────────────────┘
Paths
══════
Mail
The path to your netmail directory
BadMail
The path to your bad-message directory, used only if you have
enabled one of the move options (see below). This directory
may be your normal BadMail-directory, already used by your
EchoMail-tosser, or you can define a separate one ONLY for
TrackM.
NOTE: To be as fast as possible, TrackM will do a quick
RENAME from your Mail-directory to the BadMail-
directory. For that reason, 'Mail' and 'BadMail'
must exist on the same physical drive !!
NodeDir
The path to your nodelist directory. This is the directory
TrackM will place it's TRACKM.IDX file in.
RecMail
TrackM will move messages to the directory you set-up if they
are 'Received' and addressed to the name defined as 'Sysop'.
It's a good idea to make a special directory for that kind of
messages.
Example: D:\FD\MYMAIL
Inbound
Path where your nailer will place mail and files from nodes
you have a password with.
Unprotected
Path where your mailer will place mail and files from nodes
you don't have a password with. Leave it blank or set the
same path as 'Inbound', if you don't have such a directory.
TrackM Usermanual Version 4.20 page - 14 -
TwitMail
Path where your mailer will place mail and files from nodes
not listed in the nodelist (if you are running a BinkleyTerm-
System) or mail and files from nodes you have defined as Twit
if you are using my FDPI.EXE extension to FrontDoor. Leave
this entry blank if you don't run a 3-level inbound or insert
the same path as defined for 'Inbound'.
System
The path where TrackM look for it's files. When you start
TrackM it first attemps to find TRACKM.SYS and TRACKM.KEY in
the same directory together with TRACKM.EXE.
NOTE: You can leave this line blank. In this case TrackM
will look for its files and will also create its
files in the directory you invoke it from.
TrackM Usermanual Version 4.20 page - 15 -
Nodelist
════════
Nodelists
Filename can be a full name with extension or a name with the
extension .???. In the last case, TrackM will automatically
search for a file with the greatest numeric value for .???
Due to the new concept of the IDX-file you have to take care,
that all zones in your nodelist-files are in ascending order.
You can *never* use two files which have the same zone li-
sted. If you have for example:
SIGNODES zones 24 to 28
NODELIST zone 1 to 6
EUROLIST zone 100
you can *not* set-up a private file with one of the above
zones in it. See next statement for how to include private
nodes.
In every file, it does not matter where a zone appears. F.e.
zone 2 comes in front of zone 1 in the European fidonet-
nodelist. That's ok. If you want to include a private node-
list-file in TrackM, make sure that this file contains a zone
statement at the beginning.
Don't try to set-up something like FDPOINT.PVT! TrackM needs
a nodelist in the pure St. Louis format.
If you are running in a multitasking environment and you have
loaded SHARE, be sure to set-up a file for the first entry
which is also be used by another program. TrackM will detect
that conflict and instead of compiling a new idx, it will
work with the old ones until it has access to the nodelist
file.
Private
While TrackM can not include tiny private nodelists in it's
IDX-file, there is a 'Private-Node Manager' now. You can set-
up a maximum of 50 nodes and you are absolutely free what
addresses you put in there. Every time TrackM searches for a
valid address, it first have a quick look at your private
array.
IncludePVT
If you want to include also nodes in the IDX-file that are
marked as 'Pvt'.
IncludeHOLD
If you want to include also nodes in the IDX-file that are
marked as 'Hold' in the nodelist.
TrackM Usermanual Version 4.20 page - 16 -
Address setup
═════════════
Address <zone:net/node[.point]> [domain]
NOTE: Your main-address is hardcoded in the key if you
run the registered version. See commandline-option
-a.
Aka <zone:net/node[.point]> [domain]
Define your AKA addresses and domains. TrackM assumes '.0' if
you don't enter a pointnumber !
FakeNet
You can define a fakenet/pointnet for every Aka-address. If
you don't want to use different fakenets you *do* have to put
in your pointnet here again. Don't leave this field to zero !
Active
Only if you have set the Aka-address to be active, TrackM
takes it in account.
TrackM Usermanual Version 4.20 page - 17 -
Sysop
═════
Sysop <your name>
NOTE: Your name is hardcoded in the key if you run the
registered version.
Alias
You can define up to 10 alias-names for yourself.
R2S
Rename to sysop. A message to one of your alias-names will be
renamed to the name defined as 'Sysop'.
Act
Alias is active
Cosysops
════════
You can copy netmail addressed to you for up to 5 cosysops.
Name
Name of your cosysop.
Address
fully 4D-aware networkaddress.
NOTE: While point-checking already has taken place, you
have to define the address of a 3D-point if he is
your cosysop in the form pointnet/pointnumber.
Act
Only if 'Yes', the message will be copied. So you can leave
your cosysop(s) in this array, set them to 'No'. If you are
on vacation, you can toggle each entry to 'Yes'.
NOTE: Don't define yourself as a cosysop with the same
name as your primary sysopname. This will cause
TrackM to go into an endless loop.
TrackM Usermanual Version 4.20 page - 18 -
Languages
════════
TrackM will write it's comments in the defined language. If you
don't define a language, TrackM will write the comments in
English.
You can setup your own language in the file TRACKM.LNG. In the
registered version, you can define your own text in any language
you want for nearly all and everything. See the examples for
different languages which comes with this distribution packet.
Timezones
═════════
Having transfer with different zones in fidonet makes it difficult
to follow the time in a messages. F.e. if someone in Australia and
in USA writes a message NOW, the local timestamps would be differ
by 16 hours. So a message from Australia can reach someone in USA
before the local time.
TrackM supports Timezones in two ways:
1. If found, it will place the string defined by SET TZ=
<timezone> in the message. Possible strings are f.e.:
GMT Greenwich Mean Time
GMT+1 Greenwich Mean Time + 1 hour, that our
local time in Germany
EST Eastern Standard Time of USA
CST Central Standard Time
you can also set :
MEZ Mitteleuropäische Zeit
MESZ Mitteleuropäische Sommerzeit
but i don't think, this could help someone in Australia.
2. Timedifference to GMT (also known as UT for Universal Time)
This is an integer value between -12 and +12. This value is
interpreted as the time in hours, someone has to add or
subtract to get UT.
Here in Germany we are 1 hour in front of UT. So you have to
install -1. Someone in Australia has to install -8. Someone
in the middle of USA has to install +6.
NOTE: Even if you have defined a TZ environmentstring, you
must set the timezone to anything different from 99 in
TMSETUP to activate this function.
TrackM Usermanual Version 4.20 page - 19 -
AreaFix / AreaMgr / Raid
════════════════════════
AfterAFIX
TrackM will look for Messages to 'AreaFix' or 'AreaMgr'. If
it finds one, it will exit after everything is done, with the
errorlevel you have defined. So you can install something
like this:
TosScan Toss /NoMgr
Trackm
If Errorlevel 99 TosScan Mgr
or:
QM TOSS SCAN
TrackM
If Errorlevel 99 AreaFix
Whenever TrackM finds a message to 'AreaFix' which is from
one of your points and not already remapped to your PointNet,
it will make the remapping. This will only take place if the
message is to 'AreaFix'. Messages addressed to 'AreaMgr' will
never be changed cecause TosScan's AreaMgr can handle 4D-
addresses very well.
Tell your points to write to 'AreaFix' if you are not using
TosScan!
FixAMgr !!! TosScan Only !!!!
There is a serious bug in TosScan 1.0 that causes the
internal AreaMgr to hang up your system. 'FixAMgr' will fix
this bug. It will correct wrong messages to the right format!
This feature is only available in a FrontDoor environment.
AfterRaid
TrackM will look for Messages to 'Raid' or 'Tick'. If it
finds one, it will exit after everything is done, with the
errorlevel you have defined.
If you have defined AfterAfix & AfterRaid, TrackM will sum
both errorlevels. So if you have a 99 for AfterAfix and a 98
for AfterRaid, you will automatically have a third one of 197
if TrackM finds messages to both of them. If you run the
registered version of TrackM, i would prefer you to install
AreaFix and Raid in the Errorlevel-Manager!
4D-FixName
Name of an Area-Manager which is able to handle 4D-addresses.
This should be 'AreaMGR' for TosScan or 'AreaLink' for IMail.
If no 4D-Manager is available, enter something like 'YYYYZZZ'
to disable this function.
TrackM Usermanual Version 4.20 page - 20 -
Names and Errorlevels
═════════════════════
You can enter up to 10 names ( or substrings of a name) that
TrackM will look for in the field of the receiver. When TrackM
finds a matching name, there are two alternate methods in doing
something:
1. TrackM will end itself (after doing everything else) with an
errorlevel you have defined. If you have installed 'Rambo 30
No Yes' - and Rambo was found, TrackM will end itself with
errorlevel 30.
You can now ckeck for this situation in your batchfile with:
If Errorlevel 30 goto Rambo_found
2. Every DOS-Program can only end with one errorlevel. Therefor
TrackM knows a more powerful method of checking for a name or
up to 10 names in one run. TrackM can write out empty files
to your harddisk. If you have installed:
Rambo 30 Yes Yes
Areafix 31 Yes Yes
Jabbawooky 244 Yes Yes
and TrackM finds messages to one or all of them, it will
write out:
EXIT30.TRK
EXIT31.TRK
EXIT244.TRK
now you can install in you batchfile:
:AfterTrackM
If exist EXIT30.TRK goto Rambo_handle
If exist EXIT31.TRK goto AreaFix_handle
If exist EXIT244.TRK goto Play_a_melody
Don't forget to delete the specific file after the action has
taken place. So the last lines in your 'Rambo_handle' should
be:
DEL EXIT30.TRK
goto AfterTrackM
You can also define two ore more names with the same
errorlevel and/or file. F.e. AreaFIX and AreaMGR.
TrackM Usermanual Version 4.20 page - 21 -
Messagebits
═══════════
AddPriv
TrackM will add a 'Private' bit to all messages marked 'In
Transit'. So your users can't read messages if the sender has
forgotten to set the private-bit.
StripCrash
When tracking a message, TrackM will delete the 'Crash'-bit
of the message.
StripTransit
TrackM will strip the 'In Transit'-bit of the message.
StripOrphan
TrackM will strip the 'Orphan'-bit of returned messages.
StripFA
TrackM will strip the 'Fileattach' bit of a message 'In
Transit'.
RouteFiles *
Some mailers are not able to route files through your system
even if you want it. The file is laying around in your
inbound directory and the message is a fileattach for a file
without any information where this files exists. Tell TrackM
the path to your inbound-directory and enable 'RouteFiles'.
TrackM will insert the path to your inbound-dir into every
message, which is a fileattach marked 'In Transit', and not
already has the proper inbound-path in the subject-field.
NOTE: 'RouteFiles' will disable 'StripFA' !!
You must have defined at least one inbound path! TrackM also
takes care if a file was moved to another level inbound and
inserts the correct path.
StripFlags
This is a very important feature for all FrontDoor 1.99c
systems. Without it, it is possible that someone routes a
message to you and your system will immediately dial out to
the destination system.
AND THAT WILL EVEN WORK WITH FILEREQUESTS !
Be sure to set 'StripFlags' in your configuration file!!
'StripFlags' only kills the IMM flag and leaves the other
flags untouched.
Stripflags is only active in a FRODO or DBRIDGE environment.
TrackM Usermanual Version 4.20 page - 22 -
MatchNetwork
If a message is coming through your system and the origin-
address is not in your network, TrackM will search your Akas
if you are also a member of the destination network. If so,
TrackM will automatically change to the Aka-Address and, if
defined, to the Aka-domain.
Examples:
I am also working as a HUB 2300 for Network 507.
For all messages that are coming from Nodes not in MY Network
241, TrackM will represent itself as 2:507/2300@fidonet if
the message is TO a 507 node.
I am also a Host in SigNet
For all messages going through my SigNet Host, TrackM will
represent itself as 27:1349/0@signet
NOTE: If you have more than one Aka in another Network,
make sure to set-up the Aka you want TrackM to take
as the last entry.
AddINTL
TrackM can add INTL-lines to messages that are going THROUGH
your system if a INTL-line is necessary but missing !
Example:
27:1349/101 writes a message to 27:349/0. While both
addresses are in the same zone, there is no INTL-line in the
message.
Without 'AddINTL' this message would go to 2:349/0 ! Now
TrackM checks if there is also an address 349/0 in the zone
it finds the origin-address of the message. While this is
true, TrackM can add the INTL-line and the message will go to
the right destination.
Defaultzone
If Trackm does not find any zone-information in a message it
assumes the zone as the zone you have given with your
mainaddress. This should prevent TrackM from not finding bad
addresses where two nets exist in different zones.
TrackM Usermanual Version 4.20 page - 23 -
Message clean-up
═══════════════
CleanFreq *
TrackM will look for messages that are filerequests and are
already received by your system. Normally these messages are
laying around until you delete them manually. TrackM will
kill all filerequests that does not have the LOCAL-bit set.
KillRec *
TrackM will kill messages that are already read.
MoveRec *
Instead of killing a message that is addressed to YOU and
already read by you, TrackM will move the message to the
directory you have defined in the path section. You must also
activate 'KillRec' to use this feature.
KillSent
TrackM will kill messages that are marked as SENT.
CopyToBad
TrackM will copy messages with unknown origin or destination
addresses to the area defined in BADMAIL. Then TrackM will
process the message as usual.
MoveBadOrg
TrackM will move messages with unknown origin to the area
defined in BADMAIL. The messages are already prepared when
they are moved. So you only have to move them back to your
netmail-directory.
MoveBadDest
TrackM will move messages with unknown destination to the
area defined in BADMAIL. The messages are already prepared
when they are moved. You have to move them back to your
netmail-directory to send them out.
Move Mysent
TrackM will move messages written by YOU after they have been
marked as SENT to the directory you have defined for received
mail. So you can follow up also your replies if you have
enabled 'Move Rec' & and this option.
TrackM Usermanual Version 4.20 page - 24 -
NoEcho
TrackM will return messages that are looking like netrouted
echomail-messages back to the sender. This means TrackM will
return the message to the system it has it got from, *NOT* to
the originator of the message.
NOTE: You cannot use this function if you are using a
mailprozessor that imports echomail through your
netmail directory.
Return Orphan *
If you act as a gateway for another network - for example
UUCP - you should run a software which checks the correct
addressing and syntax of a message. If an error was found
your software should mark the message 'ORPHAN'. TrackM will
return this message to the sender. You can define your own
text for the returncomment in TRACKM.ORP.
AddReqText *
Default 'No'. You can choose wether or not TrackM should add
a text of the originator to a message made by the 'Request-
Manager'. If 'No' a empty request message is generated.
TrackM Usermanual Version 4.20 page - 25 -
The Pointnet
════════════
PointNet
Your point network-number, if you can't set the the environ-
ment-string POINTNET. See also 'Aka', if you want to run with
multiple pointnets.
DoRemap
Remap Messages from and to Points. You can toggle this
statement with the commandline-option -r at runtime.
NOTE: Only if you activate 'DoRemap' you will have access
to the other options to set-up a pointnet!
OldPointnet
I'd just changed my point network. But there are still coming
a lot of messages to the addresses of the old PointNet.
Everytime a message is coming to the OldPointNet, TrackM will
check for the correct name as defined in the 'Point-Manager'.
Also the remapping logic of messages FROM points will check
every message for the names listed in the 'Point-Manager'. So
if you install 'OldPointNet', there could never be a wrong
address from/to your points. But make sure to have all names
listed in the 'Point-Manager'!
RAXPoint *
A pointnumber your RAX points are running with. If TrackM
finds a message to Net/Node.RAXPoint, the RAXPoint will be
stripped and the message attribute is set to private only. So
you no longer have to 'KillTransit' and you don't have to
set-up your RAX points as users.
MatchFrom
Works similar to 'OldPointNet'. Every message is checked
against the name-table of the 'Point-Manager', regardless
which address is listed as origin. If the name is found,
TrackM changes the originaddress to zone:net/node.point
MatchTo
If active, EVERY message is checked against the nametable in
the 'Point-Manager'. If a name is found, TrackM will change
the destination-address to zone:PointNet/Point or, if the
point is a 4D-Point, to zone:Net/Node.Point
This will also work, if you have defined yourself as a point
of your system.
TrackM Usermanual Version 4.20 page - 26 -
NOTE: If you activate MatchFrom AND MatchTo there is no
need to activate 'OldPointnet'.
Be carefully with the names in the 'Point-Manager' if you
activate 'MatchTo'. If f.e. a message is addressed to 'Frank
Miller' of 2:310/19 and you have a 'Miller' defined as Point
1, the message will be remapped to zone:PointNet/1.
Interzonehandling:
Whenever TrackM finds a ^AINTL line in a message it will also
search for the origin- and destination-node in this line, in its
IDX file. If you see a message returned by TrackM and the address
in the destination-field looks ok, have a look at the INTL-line.
ShortINTL
Some editors only put a short form of the INTL kludge in the
message, where only the destination address is listed. If you
use such a editor enable this function.
NoINTLTest
If you don't want TrackM to test the INTL-line.
OnlyMyZone
If active, TrackM will only check messages from your main-
zone as defined in your main-address for bad origin and bad
destination address. If you wish, you can only compile a
nodelist from your own zone if you activate OnlyMyZone.
TrackM Usermanual Version 4.20 page - 27 -
┌──────────────────────┐
│ User definable Text │
└──────────────────────┘
** only available in the registered version **
Instead of using the default messages you can define your own text
for wrong destination and wrong origin messages. TMSETUP has a
built-in full-screen-editor (WordStar<tm> alike) that makes it
very easy for you to change your text. You don't have to take care
of the filenames, TMSETUP is making it for you. However you can
use any plain vanilla ASCII-Editor to build your texts.
All user definable should exist in the directory which is defined
as the system directory.
Filenames:
Everything in the file TRACKM.WDT is shown in a message with a
wrong destination before '--- message text follows ---' is shown.
Everything in the file TRACKM.ORP is shown in a message with a
ORPHAN bit before '--- message text follows ---' is shown.
Everything in the file TRACKM.WOR is shown in a message with a
wrong origin before '--- message text follows ---' is shown.
Everything in the file TRACKM.RTO is shown in a message returned
to a system in the Route-To Manager.
Everything in the file TRACKM.RFR is shown in a message returned
to a system in the Route-From Manager.
Everything in the file TRACKM.ASH is shown in a message to a
asshole before '--- message text follows ---' is shown.
TrackM Usermanual Version 4.20 page - 28 -
┌───────────┐
│ Templates │
└───────────┘
You can define your textfiles in any language now. TrackM knows
the following verbs in a text, which will be replaced:
%NODE% will be replaced with your address
%SYSOP% will be replaced with your name
%MYNAME% will be replaced with your firstname
%FIRSTNAME% will be replaced with the receivers
firstname
%LASTNAME% will be replaced with the receivers
lastname if any
%DATE% will be replaced with the actual date
%TIME% will be replaced with the actual time
NOTE: If TrackM has to return a message to the sending system
it first swaps the addresses and names and then checks
the templates ! In this case you have to exchange
%FIRSTNAME% and %MYNAME%.
TrackM Usermanual Version 4.20 page - 29 -
┌─────────────────────┐
│ THE MANAGER-SECTION │
└─────────────────────┘
If you want to temporarily disable one entry in any type of the
manager you can toggle the 'Active' bit to 'No'. This is extremely
useful in the user and disturb manager.
┌───────────────────┐
│ The Point Manager │
└───────────────────┘
TrackM will look if a message without any destination address
(which means with your own address) matches the name-field. If you
have activate 'MatchTo' TrackM will check EVERY message! TrackM
looks for a case insensitive substring in the message. So you can
put only the surname in the <name> field.
Entrys:
Pointnumber The nodenumber of your point in the specified
Fakenet. You can give the same number to different
points in different pointnets.
Name Name or substring of a name. Every name must be
unique. You can *NOT* set-up the same name for
different pointnets. You physically can, but TrackM
will end searching if it finds the first matching
name and the entry is active.
FakeNet The number of the pointnet this point belongs to.
If you enter a new point, TMSETUP will prompt you
with your primary pointnet.
4D The Point uses a 4D pointsoftware like FrontDoor.
No need to remap messages TO him to the fakenet
NOTE: You can define more than one name to the same
pointnumber. Simply enter the pointnumber twice with
different names.
When you leave the Point-Manager all entries will be sorted in the
order Fakenet..Pointnumber.
TrackM Usermanual Version 4.20 page - 30 -
┌───────────────────────┐
│The ReAddress-Manager │
└───────────────────────┘
TrackM will readdress messages from the first address to the
second address.
Entrys:
From Address <Zone:Net/Node.Point|-1>
To Address <Zone:Net/Node.Point|-1>
TrackM will readdress messages from the first
address to the second address.
Examples:
2:507/1.-1 27:349/0.-1 Yes
would readdress all messages that were originally addressed to
2:507/1 to the new address 27:349/0 . Additional pointinformation
will stay as it is. That means the -1 is a replacement for 'ALL'.
NOTE: You *HAVE TO* define -1 as point if you want to
readdress from zone:net/node to zone:net/node !!!
2:507/1.10 27:349/0.0 Yes
would readdress all messages that were originally addressed to
2:507/1.10 to the new address 27:349/0 . The Point 10 is stripped!
2:507/1.2 2:244/1.1102 Yes
would readdress all messages that were originally addressed to
2:507/1.10 to the new address 2:244/1.1102 .
TrackM Usermanual Version 4.20 page - 31 -
┌─────────────────┐
│The User-Manager │
└─────────────────┘
** only available in the registered version **
TrackM will send messages to <name> to the given address.
Say you are on vacations and want to read your messages at the
system of your friend. Just put your name and address in the 'User
Manager' and TrackM will send the messages to you.
Another way is to send your messages to a friend, who will manage
your system while you are on vacations.
The Useraddress is full 4D aware !
Entrys:
Name Name or part of the name. TrackM is case insensitiv when
checking the name. Unlike prior versions you not have to
join firstname and surname by an underscore.
Address Destination of the user
Activ see Point-Manager
TrackM Usermanual Version 4.20 page - 32 -
┌──────────────────────┐
│ The Disturb-Manager │
└──────────────────────┘
** only available in the registered version **
Again you are on vacations. But you don't have a system where you
can read your messages. Instead of laying around in your message
directory you can tell TrackM to return the message to the sender.
Entrys:
Address If there is no address TrackM will return ANY message.
With a address-field you can return messages to
dedicated nets and/or nodes. Also the address can only
be a subset of a full address.
Filename If you don't define a filename, TrackM will insert a
default comment. You can define your own messagetext for
the returnmessage in a file called TRACKM.DTB. If this
file exist, every disturb-message without a given
filename will get the text from TRACKM.DTB.
Activ see Point-Manager
Examples:
2:-1/-1 ZONE2.DTB Yes
will return all messages from zone 2. Text is taken from ZONE2.DTB
2:247/-1 NET247.DTB Yes
will return all messages from net 2:247 with the text in
NET247.DTB
2:507/1 SOLTAU.DTB Yes
will only return messages from 2:507/1 with the text in SOLTAU.DTB
2:507/1.2 BADPOINT.DTB Yes
will only return messages from 2:507/1.2 with the text in
BADPOINT.DTB
2:507/1.-1 BADPOINT.DTB Yes
will only return messages from all points of 2:507/1 with the text
in BADPOINT.DTB. Messages form the Node 2:507/1.0 will not be
returned.
2:241/-1 Yes
will return all messages from net 241 with the defaulttext or if
exist with the text in TRACKM.DTB
TrackM Usermanual Version 4.20 page - 33 -
┌─────────────────────┐
│ The Asshole-Manager │
└─────────────────────┘
** only available in the registered version **
If you don't like someone in a way that you will not read any
message from him and you don't like to route mail from him,
'asshole' is the right feature for you.
Instead of checking for addresses like the 'Disturb-Manager',
Asshole checks for names.
Asshole handles a message in one of the following ways:
1. If the message is addressed to the name defined as 'Sysop',
the message will simply be deleted. You will find a notice in
the logfile.
2. If the destination address is not your own system, that means
the message is 'In Transit', the message will be returned to
the sender. There is a predefined text for 'Asshole' in
TrackM, but you can define your own text in a file named
TRACKM.ASH
Entrys:
Name see Usermanager
Activ see Pointmanager
TrackM Usermanual Version 4.20 page - 34 -
┌─────────────────────┐
│ The Exclude-Manager │
└─────────────────────┘
** only available in the registered version **
You can exclude nodes from processing with several options.
Entrys:
Address Like everywhere in TMSetup *but* only 3D.
Crash Only if 'Yes', the system is allowed to send crash
messages via your system. This does *not* work with
FrontDoor > 2.00 because this mailer does not allow
routed crashmail.
Files If 'Yes', the system may route files via your system. If
you have defined 'StripFA' this stripping does not take
part for this system
Activ see Point-Manager
Examples:
2:507/1 Yes Yes Yes
2:507/1 may send crash messages and fileattaches through your
system. Messages are not checked for bad origin and destination.
2:241/1 No Yes Yes
2:241/1 may only send files through your system. Crashbit is
stripped if you have enable StripCrash. Messages are not checked.
2:507/1 No No Yes
Crashbits and Fileattaches will be stripped but messages are not
checked for bad origins. It's a good idea if your uplink is also
using TrackM to include him in this way. That will prevent TrackM
from adding a comment for a bad origin to a message that already
has a comment.
TrackM Usermanual Version 4.20 page - 35 -
┌──────────────────────┐
│ The Request Manager │
└──────────────────────┘
** only available in the registered version **
TrackM has a totally new feature that was never released in any
other program before. This new feature should be strong enough to
fit a separate program. But I like my TrackM and it has many
functions already built-in to make the new feature.
A user (normally a point, but can be anyone who has access to your
netmailarea) can make a filerequest via your system! After your
system has made the request and the request was successful the
file will be forwarded to the user. To manage this, the user must
follow some rules that looks similar to the AreaFix/AreaMgr syntax
( so your points will learn it quickly).
The message to request a file via your system must look like:
╒══════════════════════════════════════════════════╕
│ From: <Username> │
│ To : TrackM │
│ Subj: <Password> │
╞══════════════════════════════════════════════════╡
│ NAME: <filename>[ !password]CR │
│ ADDR: <zone:net/node>CR │
│ STAT: Crash <-- this line is optional │
╘══════════════════════════════════════════════════╛
Example:
From: Olaf Podszka of 2:241/5802
To : TrackM
Subj: 12345678
--------------------------------
NAME: VPIC29.ZIP
ADDR: 2:244/1
Syntax rules:
- after filename and address a carriage-Return must end the line.
If a password is added to the filename, there must be one
space between the name and the ! (just the same as if you write
a request message)
- NAME: and ADDR: must be in UPPER case with ONE space followed.
- username and password are case insensitive
- any text after the address is ignored by TrackM.
TrackM Usermanual Version 4.20 page - 36 -
Entries in the Request-Manager:
Name Name of the User
Location full 4D address.
NOTE: Setup your Points with the 4d-address here
because TrackM will first remap the address
before it looks to the Request-Manager.
KFS Kill the file after sending it to the user. Actually
this works only with systems supporting FLAGS (
FrontDoor & D'Bridge)
Imm Your Sysstem will make the request immediately,
regardless of costs if the user adds 'STAT: now' to his
message. Again this only works with FrontDoor &
D'Bridge.
Crash The user is allowed to add 'STAT: crash' to his message.
So the request message will get the status CRASH.
?* The user is allowed to include wildcards in the
filename.
Act see Pointmanager.
Security:
- not only the name, also the origin-address is checked
- User can't request files in a zone other than yours
- no magic filenames allowed
- destination is checked against your nodelist
If for one reason TrackM finds a syntax error in the request-
message, the user will get a message from TrackM that his message
was bad.
Everytime TrackM is invoked, it will look for a file TRACKMRQ.BBS
in it's system directory. If found, TrackM will check your inbound
directory for files, listed in TRACKMRQ.BBS. So you must have set-
up a inbound directory in TMSETUP to use this new feature. You
will have no access to the 'Request-Manager' until you have setup
the inbound dir.
After getting a file via the Request-Manager, TrackM writes the
filename, size, time etc. to a file called TRACKMRQ.HIS.
The commandline option LOOKHIS shows you the contents of this
file. This will make it more easy for you to share the costs to
your downlinks. There is a field 'costs' in the history record but
it will show '0' all the time. Computing costs depends on the
mailer you are using. You will find the structure of TRACKMRQ.HIS
in the file STRUCT.320. That should make it easy to update the
TrackM Usermanual Version 4.20 page - 37 -
costs-field for your mailer. There will be a program that does
this automatically for FrontDoor > 2.00.
┌──────────────────────┐
│ The Route-To Manager │
└──────────────────────┘
The Route-To manager gives you the possibility to disable routing
for nodes, nets or zones. If you receive a message from one of
your downlinks to a address you have no routing to, this message
will normally stay in your netmail directory until the end of
time. Now this message is returned to the sender with a
information that he should look for a different routing.
Fields in the manager:
Address A network address. The address could contain
wildcards.
Examples:
2:248/3 a fully qualified address
2:240/-1 all nodes in net 240, zone 2
1:-1/-1 complete zone 1
Filename A plain ASCII-textfile, the comment for the return
message is taken from. If no filename is given,
TrackM will look for TRACKM.RTO and if also not
found, it will insert a built-in text.
Act like everywhere
┌────────────────────────┐
│ The Route-From Manager │
└────────────────────────┘
Works similar to the above. All fields have the same meaning. The
default-filename is TRACKM.RFR. You can disable routing of
messages that are comming *from* special addresses whith one
exception: Messages to your own network will pass.
NOTE: Both Route-Managers are working on a node base. That
means, a message will ever be returned to the SYSOP of
the system who has sent it to you, even if the writer
was a point or a user of that system.
TrackM Usermanual Version 4.20 page - 38 -
┌─────────────────┐
│ TrackM Reminder │
└─────────────────┘
TrackM manages a database that is called the Remind-Manager. A
database similar to a userlist of a BBS holds information for
special dates and people. Records of the database are stored in a
file called REMIND.SYS. This file has an unlimited size but until
now, TrackM can 'only' handle the first 500 records.
Whenever you invoke the Reminder, TrackM will compare the actual
system date to the dates in the database. If it finds a matching
date it will generate a message.
Fields:
Date a date in the form dd/mm/yy normally the birthday
of a person.
Every Year If this field is set to 'No', TrackM will only
generate a message if the system date and the
listed date match exactly. If set to 'Yes' TrackM
will generate a message if the day and month
matches. This is the proper setting for birthday
greetings.
Name Name of the person you want to send the message to.
Address fully 4d address, you can enter addresses in short
form f.e. '.13' will be expanded to 2:241/5800.13
at my system.
Subject The subject of your message.
Filename a ASCII-textfile the messagetext is taken from.
Normally you will only need a few files. All
templates known from other sections will work. In
addition a new template %AGE% is active in the
Reminder. This should make birthday greetings look
very personal.
Freq Filerequest. If you set it to 'Yes', the subject is
taken as the name for a filerequest. So if you want
to be sure to request FD300.LZH from 2:241/5800 on
04/17/96 here you are ;-).
Crash Message will get the CRASH-bit set.
Imm Message will get the Immediate Flag (will work with
FrontDoor and D'Bridge only).
Act only records marked as active will be taken in
account.
TrackM Usermanual Version 4.20 page - 39 -
Installation:
To invoke the 'Reminder' you have to say TRACKM REMIND on the
commandline. It is recommended to run the program only *once* a
day. The best place to run is a clean-up batch short after
midnight.
┌─────────────────┐
│ Errorhandling │
└─────────────────┘
TrackM has an internal error-handler which makes it easy for you
to detect errors. When TrackM *MUST* exit with an error, it will
write out a file TRACKM.ERR that contains the errorcode and a
message what function had produced the error. In addition, TrackM
plays a short melody which should bother you enough to come to the
computer.
TrackM will exit with the errorlevel shown in TRACKM.ERR:
Errorlevel Reason
20 No nodelist directory found
19 TrackM IDX with less than 20 entrys
18 No Nodelist found
17 Not enough memory to read IDX
16 (reserved for Betatest)
15 Too many nodelistentrys
14 Maildirectory not found
13 General directory access error
12 more than 2000 messages
11 Corrupted EXE-file
10 Corrupted KEY-file (registered version only)
9-1 (reserved)
0 no Errors
TrackM Usermanual Version 4.20 page - 40 -
┌─────┐
│Bugs │
└─────┘
If you ever find bugs in TrackM, be sure to inlude a textfile
written out by TMSETUP's export-function in your message.
┌─────────┐
│ REGARDS │
└─────────┘
Many thanks to all people who helped me making TrackM stable and
powerful. Special thanks to:
Franko Mulato he wrote the Italian texts
Anders Brink he wrote the Swedish texts
Bjarne Maschoreck he wrote the Danish texts
Richard Bonebracke for the idea with the 4d-points
Frans Hagelaars bothered me to implement RAX-Support
Thomas Dobusch Betatester
Tim Flynn Betatester and USA registering side.
others:
Joaquim H. Homrighausen his FrontDoor SETUP was the master for me
to write TMSETUP.
Andrew Farmer his MsgTrack 2.11 gave me the inspiration
to write 'something like this'.
TrackM Usermanual Version 4.20 page - 41 -
┌──────────────────────┐
│ DISTRIBUTION SYSTEMS │
└──────────────────────┘
You will always get the latest version of TrackM if you request
one of the names:
TRACKM - latest official release
TRKMGER - German documentation und TMSETUP.EXE
TRKMBETA - next version of TrackM, will only run if you
have a TRACKM.KEY, no DOC's and language files
included, run at your own risk.
You can get the above files from one of the following systems:
Address Systemname Country Sysop
-----------------------------------------------------------
2:241/5801 Cygnus * + Germany Ulrich Bartelt
2:282/508 DataLink BBS Netherlands Ronald Faber
2:300/808 Intercom 007 + Switzerland Freddy Brocker
1:380/15 Infoboard * USA Tim Flynn
6:600/401 NoteBook 2 ASIA Larry Leong
* = Registering Sides
+ = HST,V32,V32B,V42B
all others: HST,V42B
TrackM Usermanual Version 4.20 page - 42 -
┌───────┐
│ INDEX │
└───────┘
%AGE% 38
%DATE% 28
%FIRSTNAME% 28
%LASTNAME% 28
%MYNAME% 28
%NODE% 28
%SYSOP% 28
%TIME% 28
-a 10
-g 10
-l 10
-q 10
-r 10, 25
3D 17, 34
4D 17, 19, 25, 29, 31, 36
4D-FixName 19
AddINTL 22
AddPriv 21
AddReqText 24
Address 16
Address setup 16
AfterAFIX 19
AfterRaid 19
Aka 16, 22
Alias 17
AreaFix 19
AreaMgr 19
Asshole 33
AUTOEXEC.BAT 12
BadMail 13
BINKLEY 12
BinkleyTerm 14
CHKIDX 9
CleanFreq 23
COMPILE 10
CopyToBad 23
Cosysops 17
D'Bridge 12, 36
DBRIDGE 12
Defaultzone 22
DoRemap 25
Errorlevel 20, 39
Exclude 34
FakeNet 16, 29
FDPI.EXE 14
Fileattach 21
FixAMgr 19
FRODO 12
FrontDoor 8, 12, 21, 29, 34, 36, 40
GOLDED 12
IDX-file 15
IMail 19
Inbound 13
TrackM Usermanual Version 4.20 page - 43 -
IncludeHOLD 15
IncludePVT 15
INTL-line 22, 26
KillRec 23
KillSent 23
KillTransit 25
Language 18, 28
Languages 11
Logfile 12
LOOKHIS 36
LOOKREQ 9
Mail 13
MatchFrom 25
MatchNetwork 22
MatchTo 25, 29
Move Mysent 23
MoveBadDest 23
MoveBadOrg 23
MoveRec 23
NodeDir 13
Nodelist 14
Nodelists 15
NoEcho 24
NoINTLTest 26
OldPointnet 25, 26
OnlyMyZone 26
Point 29
PointNet 11, 25
PROTECT 10
RAXPoint 25
Readdress 30
RecMail 13
REMIND 9, 39
REMIND.SYS 38
Reminder 38
RENUM 9
Request 35
Return Orphan 24
Route-To 37
RouteFiles 21
SET 9
SET DBRIDGE= 12
SET FD= 12
SET TRKMOPT= 12
SET TZ= 18
ShortINTL 26
StripCrash 21
StripFA 21, 34
StripFlags 21
StripOrphan 21
StripTransit 21
Sysop 17, 33
System 14
Templates 28
Textfiles 28
Timezones 18
TMSETUP 8
TosScan 19
TrackM Usermanual Version 4.20 page - 44 -
TRACKM.ASH 27, 33
TRACKM.DTB 32
TRACKM.ERR 39
TRACKM.IDX 13
TRACKM.KEY 7
TRACKM.LNG 11, 18
TRACKM.LOG 12
TRACKM.ORP 24, 27
TRACKM.RFR 27, 37
TRACKM.RTO 27, 37
TRACKM.TIM 10
TRACKM.WDT 27
TRACKM.WOR 27
TRACKMRQ.BBS 9, 36
TRKMOPT 12
TwitMail 14
UNPROT 10
Unprotected 13
UNSET 9
Useraddress 31
UUCP 24
Vacations 31
